Skip to content

feat: add CI action for publishing package to WinGet#564

Open
mdanish-kh wants to merge 2 commits into
microsoft:mainfrom
mdanish-kh:winget-ci
Open

feat: add CI action for publishing package to WinGet#564
mdanish-kh wants to merge 2 commits into
microsoft:mainfrom
mdanish-kh:winget-ci

Conversation

@mdanish-kh
Copy link
Copy Markdown

@mdanish-kh mdanish-kh commented Jan 5, 2025

This PR proposes to add a GitHub action for submitting the latest stable release to WinGet as it gets published. microsoft/winget-create is used as the tool for submitting the latest package.

Steps needed from maintainers

If the maintainers approve of these changes, they will need to do the following before merging this PR:

  • Add a repository secret named WINGET_CREATE_GITHUB_TOKEN that's a public access token (classic) with public_repo scope from the user account where the winget-pkgs fork will exist for submitting a PR. Recommend using a bot account for this purpose.

For reference, maintainers may see similar implemented actions in the following repos:

@dlevy-msft-sql dlevy-msft-sql changed the title Add CI action for publishing package to WinGet feat: add CI action for publishing package to WinGet May 11, 2026
@mdanish-kh
Copy link
Copy Markdown
Author

Just being notified of updates to this PR :D Since 2025, a couple of things changes so I've moved the workflow to the latest recommendations. These are

  • Use WINGET_CREATE_GITHUB_TOKEN as an environment variable instead of passing --token inline
  • No need for the additional sync fork step now

I've also removed the arm (arm32) installer from the workflow as it appears it's no longer supported and the latest winget-pkgs manifest only contains x64 & arm64 installers.

I've also updated the PR description to better reflect what needs to be done by the maintainers. cc @dlevy-msft-sql

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants